Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1357

reference
297-tree-1
name
1357
tree-preservation-order

undefined

297-tpo-1
uprn
address-text
point
POINT (-1.026940 50.893782)
geometry
MULTIPOLYGON (((-1.026855 50.893773,-1.026859 50.893789,-1.026871 50.893804,-1.026889 50.893817,-1.026913 50.893824,-1.026939 50.893827,-1.026966 50.893825,-1.026990 50.893817,-1.027009 50.893806,-1.027021 50.893791,-1.027026 50.893774,-1.027022 50.893757,-1.027010 50.893742,-1.026992 50.893730,-1.026968 50.893722,-1.026942 50.893719,-1.026915 50.893722,-1.026891 50.893729,-1.026872 50.893741,-1.026860 50.893756,-1.026855 50.893773)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL